VMware Horizon Management User Guide

Overview

This DEX Pack shows performance and usage data for VMware Horizon virtual machines. Use this DEX Pack to assess provisioning needs, system issues, and user concurrency. This data can be organized by desktop pools, virtual machines, and users.

Machine Rightsizing

Assess provisioning of virtual machines. Determine which specific metrics are over-provisioned or under-provisioned.

Pooled User Health and Concurrency

View usage and performance issues for desktop pools.

Protocol Performance

View data metrics for VMware protocols. Identify sessions with high data transfer.

Sensor Details

Identify and troubleshoot specific system issues affecting VMware hosts.

Machine Rightsizing

Global Filters

Default values for CPU Sizing, Memory Sizing, and C Drive Free space thresholds are taken from the values defined in Configure > Administration > Hardware Refresh.

Default values for CPU, Memory, and Disk (Free)thresholds are taken from the values defined in Configure > Administration > Hardware Refresh.

You can also adjust the thresholds in the dashboard to determine how the system category outcome could change.

Default CPU Sizing and Memory Sizing is based on Average Active Utilizationor Maximum Utilization.

Default C Drive Sizing is based on % free space. This can be changed to GB free space.

NOTE: The data in this dashboard is filtered only to reflect specific technology related VMware data.

System Category Breakdown by System Resource

The Group filter can be used to filter the entire dashboard to a particular SysTrack group.

There are four defined outcomes for a system: Upgrade, Replace, Review, and No change. Each metric can affect the outcome category.

Upgrade

  • The system has average memory use above the upper threshold.

  • The system has C: disk free % below the threshold.

Replace

  • The system has an average CPU use above the upper threshold and health below 90%.

Review

  • The system has an average CPU use below the lower threshold.

  • The system has an average MEM use below the lower threshold.

  • The system has an average CPU use above the upper threshold and health above 90%.

No Change

  • The system does not fall into any of the other categories.

You can click on each category to filter the System Model Summary grid to the systems in each category.

System List and Details

This grid shows each individual system and it’s relevant refresh or replacement detail.

Memory Suggestion – The suggested memory increase for the system, the system memory use needs review or no change.

CPU Suggestion – The system requires a review of the CPU use, or a system replacement (CPU is generally not upgradable).

Disk Suggestion – The system requires an upgrade to it’s disk size or no change.

Other information is also included for prioritization of potential replacement or upgrade, such as the system age or health score.

ESX Server Sizing

This table suggests the total CPU, RAM, and Disk capacity needed to achieve right sized provisioning for all systems. Filter this data using the drop-downs in the Global Filters pane.

Use the Overhead % slider to adjust the extra provisioning for all metrics. For example, if Overhead % is set to 5, then this calculation assumes 5% additional CPU, RAM, and Disk capacity for every system. Every system will be slightly over-provisioned. This helps prevent performance issues if your users begin using slightly more resources than they previously have.

Pooled User Health and Concurrency

Desktop Pools Usage and Health

This table shows session and health score data for VMware desktop pools. For more infon creating and configuring these desktop pools, refer to VMware’s documentation.

Average Session Health shows the percentage of time where productivity was not negatively impacted by system issues. System issues can include a variety of factors such as latency, CPU utilization, and disk utilization. In general, a lower Health Score indicates that a system is affected by system issues more often. This score is an average for every session in this desktop pool.

For example, consider a desktop pool with an Average Session Health of 85. On average, these sessions were negatively impacted by system issues for 15% of their active time. If a session was active for 10 hours, then it was likely impacted by system issues for about 1.5 hours.

The color coding for Average Session Health is as follows:

Red Less than 70
Yellow Between 70 and 90
Green Greater than 90

Click a desktop pool to populate the data in User Concurrency, Top 5 Health Concerns, and Top 25 Users by Session Time

User Concurrency (Selected Desktop Pool)

This graph shows the number of active sessions for the desktop pool selected in Desktop Pools Usage and Health. This data is shown every hour.

Top 5 Health Concerns (Selected Desktop Pool)

This graph shows the top 5 types of system issues impacting the desktop pool selected in Desktop Pools Usage and Health. Troubleshoot these issues to improve the user experience for users in this desktop pool.

Users by Session Time (Selected Desktop Pool)

This grid shows the users with the longest cumulative session time for the desktop pool selected in Desktop Pools Usage and Health.

Click a user to populate the data in Health Trendand Health Impact Breakdown.

Health Trend (Selected User)

This graph shows the health trend for the user selected in Top25 Users by Session Time.

Health Impact Breakdown (Selected User)

This grid shows how much each type of system issue impacted the user selected in Top 25 Users by Session Time. For each system issue, this data shows the average number of minutes affected by that issue during every session. Troubleshoot prominent system issues to improve the user experience for this user.

Protocol Performance

Performance Summary

This grid shows data metrics for VMware protocols. Each metric is averaged from every session using that protocol over the past 30 days. Each metric is related to data sent or received via the corresponding VMware protocol. For more information on these metrics, refer to VMware’s documentation.

Click a metric to populate the data in Performance Trend and Session Details.

Performance Trend (Selected Metric)

This graph shows data for the metric selected in Performance Summary. Specifically, it shows the daily average across all VMware sessions using that protocol for the past 30 days.

Click any point on this graph to populate the table in Session Details.

Session Details (Selected Metric and Date)

This grid shows the worst performing sessions for the metric and date selected inPerformance Trend. By default, the worst 25% of sessions are shown. Use the slider to adjust this value.

Double-click a system to view the performance trend for this specific system, metric, and date in Resolve. High rates of data transfer may increase latency or other performance issues on this system. Use the Health page in Resolve to investigate performance issues for the selected system, and troubleshoot those issues as needed.

Sensor Details

Triggered Sensors

This grid lists all sensors relevant to VMware hosts that triggered in the past 30 days. It also shows which sensors are currently active on VMware hosts. If any VMware-specific sensors are triggered, they are shown at the top of the grid.

Click a sensor to populate the other panes in this Dashboard. Double-click a sensor to view additional sensor info in Prevent.

Sensor Description (Selected Sensor)

This pane shows the description for the sensor selected in Triggered Sensors.

Active Sensor Trend (Selected Sensor)

This graph shows the number of VMware hosts that triggered the sensor selected in Triggered Sensors. This data is shown every day for the past 30 days.

System Details (Selected Sensor)

This table shows all the VMware hosts that triggered the sensor selected in Triggered Sensors. This data is from the past 30 days. Double-click an online system to investigate it more closely in Resolve.